Skip to content

Conversation

@arpandhakal
Copy link
Collaborator

Changes

  • Simply fetching the content changes of the editor on useAppControls was not reactive because of the internals of tiptap. Had to update the setting's content on zustand store using onUpdate callback on the editor's hook and made the content change to be listened on the setting's content instead of the content provided directly by the editor.

Testing Criteria

@arpandhakal arpandhakal requested a review from rrojan February 9, 2026 06:28
@arpandhakal arpandhakal self-assigned this Feb 9, 2026
@linear
Copy link

linear bot commented Feb 9, 2026

@vercel
Copy link

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
client-home-v3 Ready Ready Preview, Comment Feb 9, 2026 6:28am

Request Review

Copy link
Collaborator

@priosshrsth priosshrsth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Comment on lines +41 to +45
onUpdate: ({ editor }) => {
settingsStoreApi?.getState().setSettings({
content: editor.getHTML(),
})
},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried doing this but sometimes the editor got jittery / too laggy... can you stress test this fix with a lot of content + media to confirm

@arpandhakal arpandhakal merged commit 20f81ce into main Feb 9, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants